Data storage method, storage server, and storage medium and system

ABSTRACT

The present disclosure provides a data storage method, belonging to the field of data processing. The method is applied to a storage server in a cloud storage system. The method includes: monitoring data transmission status of a data acquisition device; obtaining data exception information according to the monitored data transmission exceptional status; transmitting a first data backhaul request to the data acquisition device, the data acquisition device being configured to return first data acquired within the exception time period upon receiving the first data backhaul request; and storing the first data upon receiving the first data.

This application is a National Phase of International Application No.PCT/CN2018/087912, filed on May 22, 2018 and entitled “DATA STORAGEMETHOD, STORAGE SERVER AND SYSTEM”, which claims priority to ChinesePatent Application No. 201710369637.1, filed on May 23, 2017 andentitled “DATA STORAGE METHOD, STORAGE SERVER, AND STORAGE MEDIUM ANDSYSTEM”, each of which is hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

The present disclosure relates to the field of data processing, and moreparticularly, relates to a data storage method, a storage server, and astorage medium and system.

BACKGROUND

The cloud storage technology refers to the technology integrating alarge number of storage servers in a network via application software bymeans of functions such as a cluster application, the network technologyor a distributed file system to jointly provide data storage and dataaccess functions. Upon acquiring data, a data acquisition device at afront end may store the data in a storage server by the cloud storagetechnology, thereby providing an effective assurance for long-termstorage of the data, and enabling users to connect any terminal to thestorage server anytime and anywhere for conveniently accessing the data.

SUMMARY

Embodiments of the present disclosure provide a data storage method, astorage server, and a storage medium and system. The technical solutionsare as follows.

In one aspect, a data storage method is provided. The method is appliedto a storage server in a cloud storage system. The method includes:

monitoring data transmission status of a data acquisition device, thedata acquisition device being configured to transmit acquired data tothe storage server;

obtaining data exception information according to the monitored datatransmission exceptional status, the data exception informationincluding exception start time and exception end time, the exceptionstart time and the exception end time being used to determine anexception time period;

transmitting a first data backhaul request to the data acquisitiondevice, the first data backhaul request including the data exceptioninformation, the data acquisition device being configured to returnfirst data acquired within the exception time period upon receiving thefirst data backhaul request; and

storing the first data upon receiving the first data.

In a possible implementation, the monitoring data transmission status ofa data acquisition device includes at least one of:

monitoring whether a data link between the storage server and the dataacquisition device is normal or not;

monitoring whether data transmitted by the data acquisition device isnormal or not;

monitoring whether the data transmitted by the data acquisition deviceis normally written to the storage server or not.

In another possible implementation, the obtaining data exceptioninformation according to the monitored data transmission exceptionalstatus includes:

generating data exception information when monitoring that the datatransmission status of the data acquisition device is exceptional, thedata exception information including the exception start time;

adding the exception end time into the data exception information whenmonitoring that the data transmission status of the data acquisitiondevice resumes to normal.

In another possible implementation, the cloud storage system furtherincludes a management server, and the method further includes:

receiving a first data storage task delivered by the management server,the first data storage task including a designated data acquisitiondevice identifier and a first time period; and

storing, based on the first data storage task, data transmitted by adesignated data acquisition device within the first time period.

In another possible implementation, upon the storing, based on the firstdata storage task, data transmitted by a designated data acquisitiondevice within the first time period, the method further including:

transmitting a storage record to the management server, the storagerecord including the designated data acquisition device identifier and acorresponding storage time period, the storage time period being a timeperiod during which the data transmitted by the designated dataacquisition device has been stored, the management server beingconfigured to compare the storage record with the first data storagetask, and deliver a second data storage task when determining that thestorage time period does not include a second time period within thefirst time period, the second data storage task including the designateddata acquisition device identifier and the second time period;

transmitting a second data backhaul request to the designated dataacquisition device upon receiving the second data storage task deliveredby the management server, the second data backhaul request including thesecond time period, the designated data acquisition device beingconfigured to return second data acquired within the second time periodupon receiving the second data backhaul request; and

storing the second data upon receiving the second data.

In another possible implementation, upon the storing, based on the firstdata storage task, data transmitted by a designated data acquisitiondevice within the first time period, the method further includes:

comparing the storage record with the first data storage task, andtransmitting a second data backhaul request to the designated dataacquisition device when determining that the storage time period doesnot include the second time period within the first time period, thesecond data backhaul request including the second time period, thedesignated data acquisition device being configured to return seconddata acquired within the second time period upon receiving the seconddata backhaul request; and

storing the second data upon receiving the second data.

In another aspect, a storage server is provided. The storage server isapplied to a storage server in a cloud storage system. The storageserver includes:

a monitoring module, configured to monitor data transmission status of adata acquisition device, the data acquisition device being configured totransmit acquired data to the storage server;

wherein the monitoring module is further configured to obtain dataexception information according to the monitored data transmissionexceptional status, the data exception information including exceptionstart time and exception end time, the exception start time and theexception end time being used to determine an exception time period;

a backhaul executing module, configured to transmit a first databackhaul request to the data acquisition device, the first data backhaulrequest including the data exception information, the data acquisitiondevice being configured to return first data acquired within theexception time period upon receiving the first data backhaul request;and

a storing module, configured to store the first data upon receiving thefirst data.

In another possible implementation, the monitoring module is furtherconfigured to perform at least one of the following steps:

monitoring whether a data link between the storage server and the dataacquisition device is normal or not;

monitoring whether data transmitted by the data acquisition device isnormal or not;

monitoring whether the data transmitted by the data acquisition deviceis normally written to the storage server or not.

In another possible implementation, the monitoring module is furtherconfigured to generate data exception information when monitoring thatthe data transmission status of the data acquisition device isexceptional, the data exception information including the exceptionstart time; and

the monitoring module is further configured to add the exception endtime into the data exception information when monitoring that the datatransmission status of the data acquisition device resumes to normal.

In another possible implementation, the cloud storage system furtherincludes a management server, and the storage server further includes:

a receiving module, configured to receive a first data storage taskdelivered by the management server, the first data storage taskincluding a designated data acquisition device identifier and a firsttime period; wherein

the storing module is configured to store data transmitted by thedesignated data acquisition device within the first time period based onthe first data storage task.

In another possible implementation, the storage server further includes:

a transmitting module, configured to transmit a storage record to themanagement server, the storage record including the designated dataacquisition device identifier and a corresponding storage time period,the storage time period being a time period during which the datatransmitted by the designated data acquisition device has been stored,the management server being configured to compare the storage recordwith the first data storage task, and deliver a second data storage taskwhen determining that the storage time period does not include a secondtime period within the first time period, the second data storage taskincluding the designated data acquisition device identifier and thesecond time period; wherein

the backhaul executing module is configured to transmit a second databackhaul request to the designated data acquisition device uponreceiving the second data storage task delivered by the managementserver, the second data backhaul request including the second timeperiod, the designated data acquisition device being configured toreturn second data acquired within the second time period upon receivingthe second data backhaul request; and

the storing module is configured to store the second data upon receivingthe second data.

In another possible implementation, the storage server further includes:

an integrity comparing module, configured to compare the storage recordwith the first data storage task; wherein

the backhaul executing module is further configured to transmit a seconddata backhaul request to the designated data acquisition device whendetermining that the storage time period does not include the secondtime period within the first time period, the second data backhaulrequest including the second time period, the designated dataacquisition device being configured to return second data acquiredwithin the second time period upon receiving the second data backhaulrequest; and

the storing module is further configured to store the second data uponreceiving the second data.

In another aspect, a storage server is provided. The storage serverincludes a processor and a memory, wherein at least one instruction isstored in the memory stores and loaded and executed by the processor toperform the following operations:

monitoring data transmission status of a data acquisition device, thedata acquisition device being configured to transmit acquired data tothe storage server;

obtaining data exception information according to the monitored datatransmission exceptional status, the data exception informationincluding exception start time and exception end time, the exceptionstart time and the exception end time being used to determine anexception time period;

transmitting a first data backhaul request to the data acquisitiondevice, the first data backhaul request including the data exceptioninformation, the data acquisition device being configured to returnfirst data acquired within the exception time period upon receiving thefirst data backhaul request; and

storing the first data upon receiving the first data.

In another possible implementation, the at least one instructions isloaded and executed by the processor to perform at least one of thefollowing operations:

monitoring whether a data link between the storage server and the dataacquisition device is normal or not;

monitoring whether data transmitted by the data acquisition device isnormal or not;

monitoring whether the data transmitted by the data acquisition deviceis normally written to the storage server or not.

In another possible implementation, the at least one instruction isloaded and executed by the processor to perform the followingoperations:

generating data exception information when monitoring that the datatransmission status of the data acquisition device is exceptional, thedata exception information including the exception start time; and

adding the exception end time into the data exception information whenmonitoring that the data transmission status of the data acquisitiondevice resumes to normal.

In another possible implementation, the at least one instruction isloaded and executed by the processor to perform the followingoperations:

receiving a first data storage task delivered by the management server,the first data storage task including a designated data acquisitiondevice identifier and a first time period; and

storing data transmitted by a designated data acquisition device withinthe first time period based on the first data storage task.

In another possible implementation, the at least one instruction isloaded and executed by the processor to perform the followingoperations:

transmitting a storage record to the management server, the storagerecord including the designated data acquisition device identifier and acorresponding storage time period, the storage time period being a timeperiod during which the data transmitted by the designated dataacquisition device has been stored, the management server beingconfigured to compare the storage record with the first data storagetask, and deliver a second data storage task when determining that thestorage time period does not include a second time period within thefirst time period, the second data storage task including the designateddata acquisition device identifier and the second time period;

transmitting a second data backhaul request to the designated dataacquisition device upon receiving the second data storage task deliveredby the management server, the second data backhaul request including thesecond time period, the designated data acquisition device beingconfigured to return second data acquired within the second time periodupon receiving the second data backhaul request; and

storing the second data upon receiving the second data.

In another possible implementation, the at least one instruction isloaded and executed by the processor to perform the followingoperations:

comparing the storage record with the first data storage task, andtransmitting a second data backhaul request to the designated dataacquisition device when determining that the storage time period doesnot include the second time period within the first time period, thesecond data backhaul request including the second time period, thedesignated data acquisition device being configured to return seconddata acquired within the second time period upon receiving the seconddata backhaul request; and

storing the second data upon receiving the second data.

In another aspect, a computer-readable storage medium is provided. Atleast one instruction is stored in the computer-readable storage mediumand loaded and executed by a processor to perform the operations in themethod according to the above aspect.

In another aspect, a cloud storage system is provided. The systemincludes a storage server; wherein

the storage server is configured to perform the method according to theabove aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

For clearer descriptions of the technical solutions in the embodimentsof the present disclosure, the following briefly introduces theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showmerely some embodiments of the present disclosure, and a person ofordinary skill in the art may also derive other drawings and descriptionand fall within the scope of the disclosure herein.

FIG. 1 is a schematic structural diagram of a cloud storage systemaccording to an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of an implementation environment accordingto an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of another implementation environmentaccording to an embodiment of the present disclosure;

FIG. 4 is a flowchart of a data storage method according to anembodiment of the present disclosure;

FIG. 5 is a flowchart of a data storage method according to anotherembodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a storage server accordingto an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of another storage serveraccording to an embodiment of the present disclosure;

FIG. 8 is a flowchart of a data storage method according to anotherembodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a storage server accordingto another embodiment of the present disclosure; and

FIG. 10 is a schematic structural diagram of a storage server accordingto another embodiment of the present disclosure.

DETAILED DESCRIPTION

The technical solutions in embodiments of the present disclosure areclearly and completely described hereinafter with reference toaccompanying drawings of the embodiments of the present disclosure. Itis apparent that the described embodiments are a part of the embodimentsof the present disclosure, but not all the embodiments. All otherembodiments obtained by those skilled in the art based on theembodiments of the present disclosure fall within the scope of thepresent disclosure.

Embodiments of the present disclosure provide a cloud storage system.The cloud storage system includes a storage server 101, configured tostore data acquired by a data acquisition device.

In one possible implementation, the cloud storage system may include aplurality of storage servers 101, which are configured to store dataacquired by the data acquisition device.

In another possible implementation, with reference to FIG. 1, the cloudstorage system may further include a management server 102, which may beconfigured to manage data storage of the storage server 101, forexample, managing the data acquisition device of transmitting data tothe storage server 101, and storing a time period during which thestorage server 101 stores the data.

In a case where the cloud storage system includes the plurality ofstorage servers 101, the management server 102 may be a serverindependent of the plurality of storage servers 101, and the managementserver 102 is connected to the plurality of storage servers 101 via anetwork to manage the plurality of storage servers 101.

Alternatively, the management server 102 may be one storage server 101of the plurality of storage servers 101 and may be connected to theother storage servers 101 of the plurality of storage servers 101 over anetwork. The management server 102 has the functions of both storage andmanagement. That is, the management server 102 may serve as the storageserver 101 to store data, or may serve as the management server 102 tomanage the plurality of storage servers 101. The management server 102may be selected from the plurality of storage servers 101. For example,the management server 102 may be a server randomly selected from theplurality of storage servers 101, or may be the storage server 101 witha powerful processing capability among the plurality of storage servers101. Moreover, in an actual application process, when the currentmanagement server 102 fails to operate normally since an exceptionoccurs therein, one management server 102 may be re-selected from theremaining storage servers 101.

Embodiments of the present disclosure further provide an implementationenvironment. FIG. 2 is a schematic diagram of an implementationenvironment according to an embodiment of the present disclosure. Theimplementation environment includes a cloud storage system and a dataacquisition device 103, wherein the data acquisition device 103 isconnected to the cloud storage systems over a network.

The data acquisition device 103 is configured to acquire various typesof data, such as video data, audio data, and the like. The dataacquisition device 103 may be an Internet Protocol camera (IPC), annetwork video recorder (NVR), a digital video recorder (DVR), or thelike. After the data acquisition device 103 acquires the data, theacquired data is transmitted the storage server 101 in the cloud storagesystem. The storage server 101 is configured to store the data acquiredby the data acquisition device 103 for a user to query or download.

In one possible implementation, FIG. 3 is a schematic diagram of anotherimplementation environment according to an embodiment of the presentdisclosure. The implementation environment includes a cloud storagesystem, a data acquisition device 103 and a terminal 104. With referenceto FIG. 3, the terminal 104 is connected to the management server 102via a network, may deliver a data acquisition task to the storage server101 by the management server 102, or may access the storage server 101by the management server 102 for performing management operations suchas querying, downloading and modifying on the data stored in the storageserver 101.

The embodiment of the present disclosure may be applied to variousscenarios for acquiring data. For example, an IPC is disposed in acertain place, video monitoring is performed by the IPC, and theacquired video data is stored in the cloud storage system. Moreover, avideo monitoring task may be delivered to the IPC via a terminal, andthe operations such as querying, downloading and modifying are performedon the monitored video data.

FIG. 4 is a flowchart of a data storage method according to anembodiment of the present disclosure. An execution subject in theembodiment of the present disclosure is a storage server in the cloudstorage system shown in the above embodiment. With reference to FIG. 4,the method includes the following steps.

In 201, data transmission status of a data acquisition device ismonitored, wherein the data acquisition device is configured to transmitacquired data to the storage server.

In 202, data exception information is obtained according to themonitored data transmission exceptional status, wherein the dataexception information includes exception start time and exception endtime, and the exception start time and the exception end time are usedto determine an exception time period.

In 203, a first data backhaul request is transmitted to the dataacquisition device, wherein the first data backhaul request includes thedata exception information, and the data acquisition device isconfigured to return first data acquired within the exception timeperiod upon receiving the first data backhaul request.

In 204, when the first data is received, the first data is stored.

In related art, the data acquisition devices are relatively dispersedlydistributed, which are easily affected by factors such as networkenvironments and the like. When the data acquisition device fails totransmit the data to the storage server, the acquired data may only bestored in the data acquisition device rather than being stored in thestorage server. As a result, the data stored in the storage server isincomplete, and thus reliability of the data may not be ensured.

The method according to the embodiments of the present disclosure canpunctually monitor an exception occurring in a process of transmittingdata to the storage server by the data acquisition device by monitoringthe data transmission status of the data acquisition device in realtime, determine the exception time period, store, in the storage server,the data acquired in the exception time period by the data acquisitiondevice. In this way, the lost data is complemented by data backhaul, theintegrity and reliability of the data are ensured, and excellentinstantaneity is achieved.

FIG. 5 is a flowchart of a data storage method according to anembodiment of the present disclosure. An interaction subject in theembodiment of the present disclosure is a data acquisition device aswell as a storage server in the cloud storage system shown in the aboveembodiment. With reference to FIG. 5, the method includes the followingsteps.

In 301, the storage server monitors data transmission status of the dataacquisition device.

In a process of acquiring the data by the data acquisition device, theacquired data may be transmitted to the storage server, and at thistime, the storage server may receive and store the data. The data mayinclude audio data, video data, image data, and the like.

In the embodiment of the present disclosure, in order to prevent dataloss caused by an exception occurring in a process of transmitting thedata to the storage server by the data acquisition device, the storageserver may monitor the data transmission status of the data acquisitiondevice, so as to find the exception punctually.

From different perspectives, the data transmission status of the dataacquisition device may be expressed in different forms. For example, thedata transmission status of the data acquisition device may includestatus of a data link between the storage server and the dataacquisition device, the transmitted data itself, or informationindicating whether the transmitted data may be written to the storageserver or not. Accordingly, the storage server may monitor the datatransmission status from different perspectives. For example, the step301 may include at least one of the following steps 3011 to 3013.

In 3011, whether a data link between the storage server and the dataacquisition device is normal or not is monitored.

The normal data link means that the data may be successfully transmittedthrough the data link, and the exceptional data link may includemultiple cases. For example, the data link is disconnected, the datalink has a too low data transmission speed, and the data link isinterfered by other links.

The data is transmitted between the storage server and the dataacquisition device through the data link. If the data link isexceptional, the storage server may not successfully receive the datatransmitted by the data acquisition device. Therefore, in order topunctually monitor the above cases, the storage server may monitorwhether the data link is normal or not in a data transmission process.

Once it is monitored that the data link is exceptional, it indicatesthat the storage server will not receive the data transmitted by thedata acquisition device, and the data acquisition device is expected toreturn the data. If it is monitored that the data link is normal, itindicates that the storage server may receive the data transmitted bythe data acquisition device, and the data acquisition device is notexpected to return the data.

In 3012, whether data transmitted by the data acquisition device isnormal or not is monitored.

The exception in the data transmitted by the data acquisition device mayinclude a plurality of cases. For example, the data is incomplete sincea part of the data is lost, the data is corrupted, or a format of thedata does not conform to a format determined by negotiation of the dataacquisition device and the storage server.

In the data transmission process, data loss or data corruption may becaused due to various reasons. That is, even if the storage serverreceives the data transmitted by the data acquisition device, the datamay not be complete data or the data may have been damaged, that is, thedata has expired.

Therefore, in order to punctually monitor the occurrence of the abovecases, upon receiving the data, the storage server may not store thedata, but monitor whether the data is normal. When the storage servermonitors that the data is exceptional, it indicates that the datareceived by the storage server is invalid data, and the data acquisitiondevice is expected to re-upload valid data. If the storage servermonitors that the data is normal, it indicates that the data received bythe storage server is the valid data, and the data is stored.

When whether the data is normal or not is monitored, whether the formatof the data is a preset format may be determined, and the preset formatmay be a format matching with the data acquisition device. For example,the data transmitted by the IPC should be in a video format. When it isdetermined that the data transmitted by the IPC only includes the audiodata, it indicates that the video data is lost.

When the format of the data is determined, a data type identifiercarried in a packet header of a data packet may be obtained, and theformat of the data is determined according to the data type identifier.

In 3013, whether the data transmitted by the data acquisition device isnormally written to the storage server or not is monitored.

Upon receiving the data, the storage server writes the data into adatabase, but the data may not be successfully written due to amisoperation or a failure of the storage server. That is, the storageserver may not successfully store the data.

Therefore, in order to punctually monitor the occurrence of the abovecases, after writing the data, the storage server may monitor whetherthe data is normally written or not. When it is determined that the datais not normally written, it indicates that the data fails to be stored,and then the data acquisition device is expected to re-upload the data.When it is determined that the data is normally written, it indicatesthat the data is successfully stored, and then the data acquisitiondevice is expected to re-upload the data.

For example, when the storage server performs an operation of writingthe data and receives an operation result of successfully writing thedata, it is determined that the data is normally written. However, whenthe storage server performs an operation of writing the data, butreceives an operation result indicative of a failure to write the data,it is determined that the data is not written normally.

In 302, data exception information is generated when the storage servermonitors that the data transmission status of the data acquisitiondevice is exceptional, wherein the data exception information includesexception start time.

In 303, exception end time is added into the data exception informationwhen the storage server monitors that the data transmission status ofthe data acquisition device resumes to normal.

In the embodiment of the present disclosure, the storage server mayobtain the data exception information according to the monitored datatransmission exceptional status, wherein the data exception informationincludes the exception start time and the exception end time, and theexception start time and the exception end time are used to determine anexception time period, such that the data within the exception timeperiod may be restored according to the data exception information afterthe data transmission status resumes to normal.

In fact, when the storage server monitors that the data transmissionstatus is exceptional, a time point, that is, the exception start time,at which an exception starts to occur is obtained, and the dataexception information including the exception start time is generated.Then, whether the data transmission status is normal or not iscontinuously monitored until the data transmission status resumes tonormal; and time, that is, the exception end time, at which the datatransmission status resumes to normal is obtained. At this time, theexception end time is added into the data exception information, and atime period determined by the exception start time and the exceptiontime period is the exception time period.

Based on the above steps 3011 to 3013, a process in which the storageserver monitors that the data transmission status resumes to normal mayinclude at least one of the following steps 3031 to 3033.

In 3031, when it is monitored that the data link between the storageserver and the data acquisition device resumes to normal, and the datatransmitted by the data acquisition device may be normally received, itis determined that the data transmission status resumes to normal.

In 3032, when it is monitored that the data transmitted by the dataacquisition device is normal data, it is determined that the datatransmission status resumes to normal.

In 3033, when it is monitored that the data transmitted by the dataacquisition device may be normally written into the storage server, itis determined that the data transmission status resumes to normal.

In addition, the data exception information includes not only theexception start time and the exception end time, but also an exceptionalcause, an exception case description, and the like. Alternatively, inorder to distinguish different data acquisition devices, the dataexception information may include a device identifier of the dataacquisition device that is exceptional; and the device identifier isused to uniquely determine the corresponding data acquisition device,and may be address information or a device number of the dataacquisition device.

FIG. 6 is a schematic structural diagram of a storage server accordingto an embodiment of the present disclosure. With reference to FIG. 6,the storage server may include a monitoring module, which may performthe above steps 301 to 303 to monitor data transmission status andgenerate data exception information when monitoring an exception.

In 304, the storage server transmits a first data backhaul request to adata acquisition device, wherein the first data backhaul requestincludes the data exception information.

With reference to FIG. 6, the storage server may further include abackhaul executing module. After obtaining the data exceptioninformation, the monitoring module may generate a data backhaul task,and transmit the data backhaul task to the backhaul executing module,wherein the data backhaul task may include the data exceptioninformation, at this time, the backhaul executing module executes thestep 304 based on the data backhaul task, so as to return data within anexception time period to the storage server.

It should be noted that the step 304 is performed after the above step303. For example, after the storage server determines that the datatransmission status resumes to normal and the exception end time isadded into the data exception information, the step 304 may beimmediately performed, so as to improve the data complementing speed.

In 305, the data acquisition device obtains first data acquired withinthe exception time period and transmits the first data to the storageserver upon receiving the first data backhaul request.

The first data backhaul information is used to request the dataacquisition device to re-upload the data acquired within the exceptiontime period.

Each time the data acquisition device acquires the data, the data may becached. Then, within the exception time period, although the storageserver obtains no normal data, the data acquisition device has cachedthe data. When the data transmission status resumes to normal and thestorage server transmits the first data backhaul request to the dataacquisition device, the data acquisition device may obtain the firstdata acquired within the exception time period from the cached data, andre-upload the first data to the storage server.

In order to ensure that the data within the exception time period may bereturned, a duration in which the data is cached may be set to a presetduration each time the data acquisition device acquires the data,wherein it should be determined that the preset duration may be greaterthan the duration of the exception based on the duration in which theexception is generally lasted, so as to ensure that the data has notbeen deleted when the data transmission status resumes to normal.Afterwards, when the duration in which the data is cached exceeds thepreset duration, the data may be deleted to avoid consuming storageresources of the data acquisition device.

Alternatively, the data acquisition device may not set the duration inwhich the data is cached. The data is cached into a database each timethe data is acquired. When the storage capacity of the database becomeszero, if the data is acquired again, original data in the database isreplaced with the currently acquired data.

In 306, upon receiving the first data, the storage server stores thefirst data.

Upon receiving the first data, the storage server re-stores the firstdata. When a storage rule used by the storage server is that the data isstored according to acquisition time, since the storage server may havestored the data uploaded by the data acquisition device before theexception time period and after the exception time period, uponreceiving the first data, the storage server may store the first dataafter the data received before the exception time period and before thedata received upon the exception time period, so as to ensure that thestored data may be arranged according to actual acquisition time.

It should be noted that the embodiment of the present disclosure isexemplarily described only as one storage server and one dataacquisition device. However, in practice, for a plurality of storageservers and a plurality of data acquisition devices, monitoring theexception of the data transmission status and returning the data may beperformed between any one storage server and any one data acquisitiondevice by using the method according to the embodiment of the presentdisclosure.

With the method according to the embodiment of the present disclosure,the exception occurring in the process of transmitting the data to thestorage server by the data acquisition device may be punctuallymonitored by monitoring the data transmission status of the dataacquisition device, the exception time period may be determined, thedata acquired in the exception time period by the data acquisitiondevice may be stored in the storage server. In this way, the lost datais complemented by data backhaul, the integrity and reliability of thedata are ensured, and excellent instantaneity is achieved. Moreover,compared with the data acquisition device, the storage server has alarger storage capacity and a stronger data processing capability, andthus ensures persistency of the data since the data is stored in thestorage server.

On the basis of the above embodiments, embodiments of the presentdisclosure further provide a data storage method. FIG. 8 is a flowchartof a data storage method according to an embodiment of the presentdisclosure. An interaction subject in the embodiment of the presentdisclosure is a storage server in a cloud storage system, as well as amanagement server, a terminal, and a designated data acquisition device.With reference to FIG. 8, the method includes the following steps.

In 401, the management server delivers a first data storage task to thestorage server.

Since the cloud storage system may include a plurality of storageservers and a plurality of data acquisition devices. For orderlymanagement of data storage, the data storage may be controlled by themanagement server.

In the embodiment of the present disclosure, the management server mayobtain the first data storage task, wherein the first data storage taskincludes a designated data acquisition device identifier and a firsttime period, and indicates that data acquired by the designated dataacquisition device within the first time period is stored. Afterwards,the management server delivers the first data storage task to thestorage server, and the storage server performs data storage based onthe first data storage task.

The data acquisition device identifier is used to determine a uniquecorresponding data acquisition device, and may be a device number, anInternet Protocol (IP) address, or the like of the data acquisitiondevice. The data storage task may be generated by the management server,or may be delivered to the management server after being generated bythe terminal connected to the management server. The terminal may be acomputer, a mobile phone, or other types of devices.

In practice, the control personnel may determine the designated dataacquisition device and the first time period on the terminal. Theterminal generates a first data storage task and then uploads the firstdata storage task to the management server. The management server maydetermine the storage server which should perform the first data storagetank, and deliver the first data storage task to the determined storageserver.

The first time period may be determined according to a monitoringrequirement of the designated data acquisition device. For example, forthe IPC, the IPC monitors a designated place, and the first time periodmay be determined according to a monitoring requirement of thedesignated place, in order to obtain video data of the designated placewithin the first time period without obtaining video data of thedesignated place in other time periods. For a hospital, only video dataof the hospital during working hours is monitored, and there is no needto monitor video data of the hospital during rest periods.

In 402, the storage server receives the first data storage taskdelivered by the management server, and stores data transmitted by thedesignated data acquisition device within the first time period based onthe first data storage task.

In the embodiment of the present disclosure, based on the first datastorage task, it is necessary for the storage server to store the datatransmitted by the designated data acquisition device within the firsttime period, but unnecessary for the storage server to store the datatransmitted by the designated data acquisition device within other timeperiods. Therefore, within the first time period, when the storageserver receives the data transmitted by the designated data acquisitiondevice, the data may be stored. Within other time periods, when thestorage server receives the data transmitted by the designated dataacquisition device, the data may not be stored.

In 403, the storage server generates a storage record, and transmits thestorage record to the management server.

After the storage server stores the data transmitted by the designateddata acquisition device, the storage record may be generated, whereinthe storage record includes the designated data acquisition deviceidentifier and a corresponding storage time period. The storage periodis a time period during which the data transmitted by the designateddata acquisition device has been stored.

In the data storage process, data may be lost since an exception occursin a communication link between the designated data acquisition deviceand the storage server or the storage server fails. In order tocomplement the lost data, the storage server may transmit the storagerecord to the management server, and the management server compares thetime period during which the data needs to be stored with an actualstorage time period.

The storage server may transmit the storage record to the managementserver after storing the data, or may transmit the storage record to themanagement server upon receiving a query request, which carries thedesignated data acquisition device identifier, transmitted by themanagement server. Accordingly, the step of performing the comparison bythe management server may be performed periodically after the storagerecord is received, or may be performed at a preset time point or at anytime point.

In 404, the management server receives the storage record, compares thestorage record with the first data storage tank, and delivers a seconddata storage task to the storage server when determining that thestorage time period does not include second time period within the firsttime period, wherein the second data storage task includes thedesignated data acquisition device identifier and the second timeperiod.

In 405, the storage server transmits a second data backhaul request tothe designated data acquisition device upon receiving the second datastorage task transmitted by the management server.

The management server compares the storage record with the first datastorage task, that is, comparing the storage time period with the firsttime period, and determining whether all the data within the first timeperiod has been stored. When it is determined that the storage timeperiod does not include the second time period within the first timeperiod, indicating that the data within the second time period is lost,the management server delivers the second data storage task to thestorage server, wherein the second data storage task includes thedesignated data acquisition device identifier and the second timeperiod. The storage server transmits a second data backhaul request tothe designated data acquisition device upon receiving the second datastorage task, to request the designated data acquisition device tore-upload the data within the second time period.

With reference to FIG. 6, the management server transmits the seconddata storage task including the designated data acquisition deviceidentifier and the second time period to the storage server whendetermining that the data within the second time period is lost, andtransmits the second data storage task to the backhaul executing module,and at this time, the backhaul executing module transmits a second databackhaul request to the designated data acquisition device based on thesecond data storage task, so as to return the lost data to the storageserver.

It should be noted that, the embodiment of the present disclosure willbe exemplarily described as follows: after the storage server generatesthe storage record, the management server compares the storage recordwith the first data storage task. However, in another embodiment, thestorage server may compare the storage record with the first datastorage task. That is, the above steps 403 to 405 may be replaced withthe following steps: the storage server generates the storage record,compares the storage record with the first data storage task, andtransmits the second data backhaul request to the designated dataacquisition device when determining that the storage time period doesnot include the second time period within the first time period.

With reference to FIG. 7, the storage server may further include anintegrity comparison module, which may perform the above comparisonstep, and generate a data backhaul task when comparing and determiningthat the data within the second time period is lost, and transmits thedata backhaul task to the backhaul executing module, wherein the databackhaul task includes the second time period. At this time, thebackhaul executing module transmits a second data backhaul request tothe designated data acquisition device according to the data backhaultask, so as to return the lost data to the storage server by thedesignated data acquisition device.

In 406, the designated data acquisition device obtains the second dataacquired within the second time period upon receiving the second databackhaul request, and transmits the second data to the storage server.

In 407, the storage server stores the second data upon receiving thesecond data.

For example, the first time period may include a third time period, asecond time period and a fourth time period in a chronological order.The storage server has stored data within the third time period and thefourth time period, but not store data within the second time period.Subsequently, when the storage server receives the second data acquiredwithin the second time period, the second data is stored after the datawithin the third time period and before the data within the fourth timeperiod, so as to ensure that the stored data is arranged in thechronological order and the rationality is improved.

In addition, the terminal may query data in the storage server. Forexample, the terminal determines a data acquisition device identifierand a time period which are to be queried, and transmits a data queryrequest to the management server. The management server transmits thedata query request to the storage server, wherein the data query requestcarries the data acquisition device identifier and the time period. Whenthe storage server receives the data query request, the storage serverobtains the data acquired by the corresponding data acquisition devicewithin the stored time period, the management server transmits the datato the terminal, and the terminal may present the data for a user toview.

Alternatively, the terminal may download the data stored in the storageserver. For example, the terminal determines a data acquisition deviceidentifier and a time period in which the data is to be downloaded, andtransmits a data download request to the management server. Themanagement server transmits the data download request to the storageserver, wherein the data download request carries the data acquisitiondevice identifier and the time period. The storage server obtains thedata acquired by the corresponding data acquisition device within thestored time period upon receiving the data download request, themanagement server transmits the data to the terminal, and the terminalmay download the data and store the data in the terminal.

With the method according to the embodiments of the present disclosure,the data loss may be punctually monitored immediately by comparing thestorage record with the data storage task, and the second time periodduring which the data is lost may be determined, and the data acquiredby the designated data acquisition device within the second time periodmay be stored in the data storage server. In this way, the lost data iscomplemented by data backhaul, the integrity and reliability of the dataare ensured, and excellent instantaneity is achieved. Moreover, comparedwith the data acquisition device, the storage server has a largerstorage capacity and a stronger data processing capability, and thusensures persistency of the data since the data is stored in the storageserver.

Based on the above embodiments shown in FIG. 5 and FIG. 8, theembodiments of the present disclosure provide a complete data integritydetection solution, which combines two methods of instant processing andtiming processing, such that the integrity of the data may be ensured.After the data transmission status between the data acquisition deviceat a current end and the storage server is exceptional or the data islost, the data may be complemented automatically.

FIG. 9 is a schematic structural diagram of a storage server accordingto an embodiment of the present disclosure. With reference to FIG. 9,the storage server includes:

a monitoring module 501, configured to monitor data transmission statusof a data acquisition device, the data acquisition device beingconfigured to transmit acquired data to the storage server;

wherein the monitoring module 501 is further configured to obtain dataexception information according to the monitored data transmissionexceptional status, the data exception information including exceptionstart time and exception end time, the exception start time and theexception end time being used to determine an exception time period;

a backhaul executing module 502, configured to transmit a first databackhaul request to the data acquisition device, the first data backhaulrequest including the data exception information, the data acquisitiondevice being configured to return first data acquired within theexception time period upon receiving the first data backhaul request;and

a storing module 503, configured to store the first data upon receivingthe first data.

In one possible implementation, the monitoring module 501 is furtherconfigured to perform at least one of the following steps:

monitoring whether a data link between the storage server and the dataacquisition device is normal or not;

monitoring whether data transmitted by the data acquisition device isnormal or not; and

monitoring whether the data transmitted by the data acquisition deviceis normally written to the storage server or not.

In another possible implementation, the monitoring module 501 is furtherconfigured to generate data exception information when monitoring thatthe data transmission status of the data acquisition device isexceptional, wherein the data exception information includes theexception start time; and

the monitoring module 501 is further configured to add the exception endtime into the data exception information when monitoring that the datatransmission status of the data acquisition device resumes to normal.

In another possible implementation, the cloud storage system furtherincludes a management server, and the storage server further includes:

a receiving module, configured to receive a first data storage taskdelivered by the management server, the first data storage taskincluding a designated data acquisition device identifier and a firsttime period;

wherein the storing module 503 is configured to store data transmittedby the designated data acquisition device within the first time periodbased on the first data storage task;

a transmitting module, configured to transmit a storage record to themanagement server, the storage record including the designated dataacquisition device identifier and a corresponding storage time period,the storage time period being a time period during which the datatransmitted by the designated data acquisition device has been stored,the management server being configured to compare the storage recordwith the first data storage task, and deliver a second data storage taskwhen determining that the storage time period does not include secondtime period within the first time period, the second data storage taskincluding the designated data acquisition device identifier and thesecond time period; wherein

the backhaul executing module 502 is configured to transmit a seconddata backhaul request to the designated data acquisition device uponreceiving the second data storage task delivered by the managementserver, the second data backhaul request including the second timeperiod, the designated data acquisition device being configured toreturn second data acquired within the second time period upon receivingthe second data backhaul request; and

the storing module 503 is configured to store the second data uponreceiving the second data.

In another possible implementation, the storage server further includes:

an integrity comparison module, configured to compare the storage recordwith the first data storage task; wherein

the backhaul executing module 502 is further configured to transmit asecond data backhaul request to the designated data acquisition devicewhen determining that the storage time period does not include thesecond time period within the first time period, the second databackhaul request including the second time period, the designated dataacquisition device being configured to return second data acquiredwithin the second time period upon receiving the second data backhaulrequest; and

the storing module 503 is further configured to store the second dataupon receiving the second data.

All of the above alternative technical solutions may be combined to formalternate embodiments of the present disclosure, which will be omittedhere.

It should be noted that during data storage by the storage serveraccording to this embodiment, description is given only using divisionof all the functional modules as an example. In practice, the abovefunctions may be implemented by the different functional modules asrequired. That is, the internal structure of the storage server isdivided into different functional modules to implement all or part ofthe functions described above. In addition, the storage server accordingto this embodiment is based on the same inventive concept as the datastorage method according to the above embodiment. For the specificimplementation of the storage server, reference may be made to themethod embodiment, which is thus not described herein any further.

FIG. 10 is a schematic structural diagram of a storage server accordingto an embodiment of the present disclosure. The storage server 600 mayvary greatly depending on different configurations or performance, andmay include one or more central processing units (CPUs) 622 (e.g., oneor more processors) and a memory 632, one or more storage media 630(e.g., one or one mass storage devices) for storing an application 642or data 644. The memory 632 and the storage medium 630 may be atransitory storage medium or a non-transitory storage media. The programstored in the storage medium 630 may include one or more modules (notshown in FIG. 6). Each of the one or more modules may include a seriesof operation instructions executable by the server. Furthermore, the CPU622 may be communicated with the storage medium 630, and the series ofoperation instructions in the storage medium 630 may be executed on thestorage server 600.

The storage server 600 may further include one or more power sources626, one or more wired or wireless network interfaces 650, one or moreinput/output interfaces 658, one or more keyboards 656, and/or one ormore operating systems 641, such as Windows Server™, Mac OS X™, Unix™,Linux™, and FreeBSD™.

The storage server 600 may be configured to perform the steps performedby the storage server in the data storage methods according to the aboveembodiments.

An embodiment of the present disclosure provides a storage server. Thestorage server includes a processor and a memory, wherein at least oneinstruction is stored in the memory stores and loaded and executed bythe processor to perform the following operations:

monitoring data transmission status of a data acquisition device, thedata acquisition device being configured to transmit acquired data tothe storage server;

obtaining data exception information according to the monitored datatransmission exceptional status, the data exception informationcomprising exception start time and exception end time, the exceptionstart time and the exception end time being used to determine anexception time period;

transmitting a first data backhaul request to the data acquisitiondevice, the first data backhaul request comprising the data exceptioninformation, the data acquisition device being configured to returnfirst data acquired within the exception time period upon receiving thefirst data backhaul request; and

storing the first data upon receiving the first data.

In one possible implementation, the at least one instruction is loadedand executed by the processor to implement at least one of the followingoperations:

monitoring whether a data link between the storage server and the dataacquisition device is normal or not;

monitoring whether data transmitted by the data acquisition device isnormal or not;

monitoring whether the data transmitted by the data acquisition deviceis normally written to the storage server or not.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

generating data exception information when monitoring that the datatransmission status of the data acquisition device is exceptional, thedata exception information comprising the exception start time; and

adding the exception end time into the data exception information whenmonitoring that the data transmission status of the data acquisitiondevice resumes to normal.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

receiving a first data storage task delivered by the management server,the first data storage task comprising a designated data acquisitiondevice identifier and a first time period; and

storing data transmitted by a designated data acquisition device withinthe first time period based on the first data storage task.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

transmitting a storage record to the management server, the storagerecord comprising the designated data acquisition device identifier anda corresponding storage time period, the storage time period being atime period during which the data transmitted by the designated dataacquisition device has been stored, the management server beingconfigured to compare the storage record with the first data storagetask, and deliver a second data storage task when determining that thestorage time period does not comprise a second time period within thefirst time period, the second data storage task comprising thedesignated data acquisition device identifier and the second timeperiod;

transmitting a second data backhaul request to the designated dataacquisition device upon receiving the second data storage task deliveredby the management server, the second data backhaul request comprisingthe second time period, the designated data acquisition device beingconfigured to return second data acquired within the second time periodupon receiving the second data backhaul request; and

storing the second data upon receiving the second data.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

comparing the storage record with the first data storage task, andtransmitting a second data backhaul request to the designated dataacquisition device when determining that the storage time period doesnot comprise the second time period within the first time period, thesecond data backhaul request comprising the second time period, thedesignated data acquisition device being configured to return seconddata acquired within the second time period upon receiving the seconddata backhaul request; and

storing the second data upon receiving the second data.

An embodiment of the present disclosure provides a computer-readablestorage medium storing at least one instruction. The at least oneinstruction may be loaded and executed by a processor to realize theoperations performed in the above method embodiments. For example, thecomputer-readable storage medium may be a read-only memory (ROM), arandom-access memory (RAM), a compact disc read-only memory (CD-ROM), amagnetic disk, a floppy disk, an optical data storage device or thelike.

The at least one instruction is loaded and executed by the processor toimplement at least one of the following operations:

monitoring data transmission status of a data acquisition device, thedata acquisition device being configured to transmit acquired data tothe storage server;

obtaining data exception information according to the monitored datatransmission exceptional status, the data exception informationcomprising exception start time and exception end time, the exceptionstart time and the exception end time being used to determine anexception time period;

transmitting a first data backhaul request to the data acquisitiondevice, the first data backhaul request comprising the data exceptioninformation, the data acquisition device being configured to returnfirst data acquired within the exception time period upon receiving thefirst data backhaul request; and

storing the first data upon receiving the first data.

In one possible implementation, the at least one instruction is loadedand executed by the processor to implement at least one of the followingoperations:

monitoring whether a data link between the storage server and the dataacquisition device is normal or not;

monitoring whether data transmitted by the data acquisition device isnormal or not;

monitoring whether the data transmitted by the data acquisition deviceis normally written to the storage server or not.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

generating data exception information when monitoring that the datatransmission status of the data acquisition device is exceptional, thedata exception information comprising the exception start time; and

adding the exception end time into the data exception information whenmonitoring that the data transmission status of the data acquisitiondevice resumes to normal.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

receiving a first data storage task delivered by the management server,the first data storage task comprising a designated data acquisitiondevice identifier and a first time period; and

storing data transmitted by a designated data acquisition device withinthe first time period based on the first data storage task.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

transmitting a storage record to the management server, the storagerecord comprising the designated data acquisition device identifier anda corresponding storage time period, the storage time period being atime period during which the data transmitted by the designated dataacquisition device has been stored, the management server beingconfigured to compare the storage record with the first data storagetask, and deliver a second data storage task when determining that thestorage time period does not comprise a second time period within thefirst time period, the second data storage task comprising thedesignated data acquisition device identifier and the second timeperiod;

transmitting a second data backhaul request to the designated dataacquisition device upon receiving the second data storage task deliveredby the management server, the second data backhaul request comprisingthe second time period, the designated data acquisition device beingconfigured to return second data acquired within the second time periodupon receiving the second data backhaul request; and

storing the second data upon receiving the second data.

In another possible implementation, the at least one instruction isloaded and executed by the processor to implement at least one of thefollowing operations:

comparing the storage record with the first data storage task, andtransmitting a second data backhaul request to the designated dataacquisition device when determining that the storage time period doesnot comprise the second time period within the first time period, thesecond data backhaul request comprising the second time period, thedesignated data acquisition device being configured to return seconddata acquired within the second time period upon receiving the seconddata backhaul request; and storing the second data upon receiving thesecond data.

Those skilled in the art may understand that all or part of the stepsaccording to the above embodiments may be implemented by hardware, ormay be implemented by related hardware instructed by a program, and theprogram may be stored in a computer-readable storage medium. The storagemedium mentioned above may be a read-only memory, a magnetic disk, anoptical disk or the like.

Described above are merely exemplary embodiments of the presentdisclosure, and are not intended to limit the present disclosure. Withinthe spirit and principles of the disclosure, any modifications,equivalent substitutions, or improvements are within the protectionscope of the present disclosure.

1. A data storage method, the method being applied to a storage serverin a cloud storage system and comprising: monitoring data transmissionstatus of a data acquisition device, the data acquisition device beingconfigured to transmit acquired data to the storage server; obtainingdata exception information according to the monitored data transmissionexceptional status, the data exception information comprising exceptionstart time and exception end time, the exception start time and theexception end time being used to determine an exception time period;transmitting a first data backhaul request to the data acquisitiondevice, the first data backhaul request comprising the data exceptioninformation, the data acquisition device being configured to returnfirst data acquired within the exception time period upon receiving thefirst data backhaul request; and storing the first data upon receivingthe first data.
 2. The method according to claim 1, wherein themonitoring data transmission status of the data acquisition devicecomprises at least one of: monitoring whether a data link between thestorage server and the data acquisition device is normal or not;monitoring whether data transmitted by the data acquisition device isnormal or not; monitoring whether the data transmitted by the dataacquisition device is normally written to the storage server or not. 3.The method according to claim 1, wherein the obtaining data exceptioninformation according to the monitored data transmission exceptionalstatus comprises: generating data exception information when monitoringthat the data transmission status of the data acquisition device isexceptional, the data exception information comprising the exceptionstart time; adding the exception end time into the data exceptioninformation when monitoring that the data transmission status of thedata acquisition device resumes to normal.
 4. The method according toclaim 1, wherein the cloud storage system further comprises a managementserver, and the method further comprises: receiving a first data storagetask delivered by the management server, the first data storage taskcomprising a designated data acquisition device identifier and a firsttime period; and storing, based on the first data storage task, datatransmitted by a designated data acquisition device within the firsttime period.
 5. The method according to claim 4, upon the storing, basedon the first data storage task, data transmitted by a designated dataacquisition device within the first time period, the method furthercomprises: transmitting a storage record to the management server, thestorage record comprising the designated data acquisition deviceidentifier and a corresponding storage time period, the storage timeperiod being a time period during which the data transmitted by thedesignated data acquisition device has been stored, the managementserver being configured to compare the storage record with the firstdata storage task, and deliver a second data storage task whendetermining that the storage time period does not comprise a second timeperiod within the first time period, the second data storage taskcomprising the designated data acquisition device identifier and thesecond time period; transmitting a second data backhaul request to thedesignated data acquisition device upon receiving the second datastorage task delivered by the management server, the second databackhaul request comprising the second time period, the designated dataacquisition device being configured to return second data acquiredwithin the second time period upon receiving the second data backhaulrequest; and storing the second data upon receiving the second data. 6.The method according to claim 4, wherein upon the storing, based on thefirst data storage task, data transmitted by a designated dataacquisition device within the first time period, the method furthercomprises: comparing the storage record with the first data storagetask, and transmitting a second data backhaul request to the designateddata acquisition device when determining that the storage time perioddoes not comprise the second time period within the first time period,the second data backhaul request comprising the second time period, thedesignated data acquisition device being configured to return seconddata acquired within the second time period upon receiving the seconddata backhaul request; and storing the second data upon receiving thesecond data. 7.-12. (canceled)
 13. A storage server, comprising aprocessor and a memory, wherein at least one instruction is stored inthe memory stores and loaded and executed by the processor to performthe following operations: monitoring data transmission status of a dataacquisition device, the data acquisition device being configured totransmit acquired data to the storage server; obtaining data exceptioninformation according to the monitored data transmission exceptionalstatus, the data exception information comprising exception start timeand exception end time, the exception start time and the exception endtime being used to determine an exception time period; transmitting afirst data backhaul request to the data acquisition device, the firstdata backhaul request comprising the data exception information, thedata acquisition device being configured to return first data acquiredwithin the exception time period upon receiving the first data backhaulrequest; and storing the first data upon receiving the first data. 14.The storage server according to claim 13, wherein the at least oneinstruction is loaded and executed by the processor to implement atleast one of the following operations: monitoring whether a data linkbetween the storage server and the data acquisition device is normal ornot; monitoring whether data transmitted by the data acquisition deviceis normal or not; monitoring whether the data transmitted by the dataacquisition device is normally written to the storage server or not. 15.The storage server according to claim 13, wherein the at least oneinstruction is loaded and executed by the processor to perform thefollowing operations: generating data exception information whenmonitoring that the data transmission status of the data acquisitiondevice is exceptional, the data exception information comprising theexception start time; and adding the exception end time into the dataexception information when monitoring that the data transmission statusof the data acquisition device resumes to normal.
 16. The storage serveraccording to claim 13, wherein the at least one instruction is loadedand executed by the processor to perform the following operations:receiving a first data storage task delivered by the management server,the first data storage task comprising a designated data acquisitiondevice identifier and a first time period; and storing data transmittedby a designated data acquisition device within the first time periodbased on the first data storage task.
 17. The storage server accordingto claim 16, wherein the at least one instruction is loaded and executedby the processor to implement the following operations: transmitting astorage record to the management server, the storage record comprisingthe designated data acquisition device identifier and a correspondingstorage time period, the storage time period being a time period duringwhich the data transmitted by the designated data acquisition device hasbeen stored, the management server being configured to compare thestorage record with the first data storage task, and deliver a seconddata storage task when determining that the storage time period does notcomprise a second time period within the first time period, the seconddata storage task comprising the designated data acquisition deviceidentifier and the second time period; transmitting a second databackhaul request to the designated data acquisition device uponreceiving the second data storage task delivered by the managementserver, the second data backhaul request comprising the second timeperiod, the designated data acquisition device being configured toreturn second data acquired within the second time period upon receivingthe second data backhaul request; and storing the second data uponreceiving the second data.
 18. The storage server according to claim 16,wherein the at least one instruction is loaded and executed by theprocessor to perform the following operations: comparing the storagerecord with the first data storage task, and transmitting a second databackhaul request to the designated data acquisition device whendetermining that the storage time period does not comprise the secondtime period within the first time period, the second data backhaulrequest comprising the second time period, the designated dataacquisition device being configured to return second data acquiredwithin the second time period upon receiving the second data backhaulrequest; and storing the second data upon receiving the second data. 19.A non-volatile computer-readable storage medium, wherein at least oneinstruction is stored in the computer-readable storage medium and loadedand executed by a processor to implement the following operations:monitoring data transmission status of a data acquisition device, thedata acquisition device being configured to transmit acquired data tothe storage server; obtaining data exception information according tothe monitored data transmission exceptional status, the data exceptioninformation comprising exception start time and exception end time, theexception start time and the exception end time being used to determinean exception time period; transmitting a first data backhaul request tothe data acquisition device, the first data backhaul request comprisingthe data exception information, the data acquisition device beingconfigured to return first data acquired within the exception timeperiod upon receiving the first data backhaul request; and storing thefirst data upon receiving the first data.
 20. A cloud storage system,comprising a storage server; wherein the storage server is configured toperform the method as defined in claim
 1. 21. The computer-readablestorage medium according to claim 19, wherein the at least oneinstruction is loaded and executed by the processor to implement atleast one of the following operations: monitoring whether a data linkbetween the storage server and the data acquisition device is normal ornot; monitoring whether data transmitted by the data acquisition deviceis normal or not; monitoring whether the data transmitted by the dataacquisition device is normally written to the storage server or not. 22.The computer-readable storage medium according to claim 19, wherein theat least one instruction is loaded and executed by the processor toperform the following operations: generating data exception informationwhen monitoring that the data transmission status of the dataacquisition device is exceptional, the data exception informationcomprising the exception start time; and adding the exception end timeinto the data exception information when monitoring that the datatransmission status of the data acquisition device resumes to normal.23. The computer-readable storage medium according to claim 19, whereinthe at least one instruction is loaded and executed by the processor toperform the following operations: receiving a first data storage taskdelivered by the management server, the first data storage taskcomprising a designated data acquisition device identifier and a firsttime period; and storing data transmitted by a designated dataacquisition device within the first time period based on the first datastorage task.
 24. The computer-readable storage medium according toclaim 23, wherein the at least one instruction is loaded and executed bythe processor to implement the following operations: transmitting astorage record to the management server, the storage record comprisingthe designated data acquisition device identifier and a correspondingstorage time period, the storage time period being a time period duringwhich the data transmitted by the designated data acquisition device hasbeen stored, the management server being configured to compare thestorage record with the first data storage task, and deliver a seconddata storage task when determining that the storage time period does notcomprise a second time period within the first time period, the seconddata storage task comprising the designated data acquisition deviceidentifier and the second time period; transmitting a second databackhaul request to the designated data acquisition device uponreceiving the second data storage task delivered by the managementserver, the second data backhaul request comprising the second timeperiod, the designated data acquisition device being configured toreturn second data acquired within the second time period upon receivingthe second data backhaul request; and storing the second data uponreceiving the second data.
 25. The computer-readable storage mediumaccording to claim 23, wherein the at least one instruction is loadedand executed by the processor to perform the following operations:comparing the storage record with the first data storage task, andtransmitting a second data backhaul request to the designated dataacquisition device when determining that the storage time period doesnot comprise the second time period within the first time period, thesecond data backhaul request comprising the second time period, thedesignated data acquisition device being configured to return seconddata acquired within the second time period upon receiving the seconddata backhaul request; and storing the second data upon receiving thesecond data.